Remove X Layer from getLogs disabled chains and implement intelligent chunking

Summary

Remove X Layer from getLogs disabled chains to unblock protocol adapters while implementing conservative chunking logic to prevent RPC overload and ensure system stability.

Changes Made

• Remove X Layer from getLogs disabled chains to unblock protocol adapters
• Implement conservative 5k block range chunking to prevent RPC overload
• Add automatic retry logic and proper error handling for large ranges
• Enable uniV3Export and other log-dependent helpers for X Layer protocols

Technical Implementation

• Replace hard cache-only restriction with intelligent chunking logic
• 5000 block maximum per request with 100ms delays between chunks
• Preserves existing performance for other chains
• Graceful fallback to cache when appropriate

Impact

• Unblocks PotatoSwap V3 adapter (referenced in PR Update potatoswap adapter (XLayer) to include V3 TVL. #16812)
• Enables standard DeFi helpers (uniV3Export, Compound forks, etc.)
• Opens X Layer ecosystem for comprehensive DeFi tracking
• Maintains system stability with conservative rate limiting

Testing Instructions

Prerequisites

• Ensure you have access to X Layer RPC endpoints
• Have the PotatoSwap V3 adapter code available for testing

Manual Testing Steps

1. Test PotatoSwap V3 Adapter

   # Navigate to the PotatoSwap adapter directory
   cd projects/potatoswap-v3
   
   # Run the adapter to verify TVL calculation
   npm test
   # or
   node index.js

   Expected: Should return TVL data without getLogs errors

2. Test Chunking Logic

   # Test with a large block range to trigger chunking
   # This can be done by temporarily modifying the adapter to use a large block range
   # Verify logs show chunking is activated (5000 block chunks with 100ms delays)

3. Test Other DeFi Helpers

   # Test uniV3Export functionality on X Layer
   # Run any X Layer adapter that uses uniV3Export
   # Verify no getLogs errors occur

4. Regression Testing

   # Test existing adapters on other chains to ensure no impact
   cd projects/[any-other-adapter]
   npm test

   Expected: No performance degradation or new errors

Automated Testing

• Run the full test suite to ensure no regressions
• Verify PotatoSwap adapter passes all tests
• Confirm getLogs functionality works correctly across all chains

Expected Results

• PotatoSwap adapter calculates TVL correctly (approximately $X amount)
• No getLogs errors during execution
• Chunking logic activates for large block ranges
• Existing chains remain unaffected
• System maintains stable performance with rate limiting

Verification Checklist

• PotatoSwap V3 adapter runs without errors
• TVL calculations are accurate
• Chunking activates for ranges > 5000 blocks
• 100ms delays are observed between chunks
• Existing adapters on other chains work normally
• No memory leaks or performance issues
• Error handling works for RPC failures